Reduce maximum wait time for get_operator_name() to fix hangups (IDFGH-12591)#547
Open
0xFEEDC0DE64 wants to merge 1 commit intoespressif:masterfrom
Open
Reduce maximum wait time for get_operator_name() to fix hangups (IDFGH-12591)#5470xFEEDC0DE64 wants to merge 1 commit intoespressif:masterfrom
0xFEEDC0DE64 wants to merge 1 commit intoespressif:masterfrom
Conversation
Collaborator
|
This command usually takes some time to complete, depending on the modem, but I see that this is more or less configurable on modern devices (e.g. Timeout set with Maybe we could add an optional timeout parameter, that would default to those 75seconds? |
github-actions
bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Is there a reason why we have to freeze the task for 75 seconds here?
We have had lots of hangups and it seems like the answer is typically there after ~100ms, not 75000ms